Domain request

ABSTRACT

A system and method for determining registration to a packet-switching (PS) domain or a circuit-switching (CS) domain via a single request is discussed herein. A single request includes a query hierarchy to query a node of a first domain and then, if the UE is not registered with the first domain, to query a node of a second domain. The request includes an attribute value pair (AVP) to determine which domain to query first and which node of the first domain to query. The domains of the AVP are acquired from a list to permit multiple domains to be queried with the single request.

BACKGROUND

An application server of a telecommunications network can query adomain, whether packet-switched or circuit-switched, to determine thedomain to which a user equipment is registered. By establishing theregistered domain, the application server can determine the servicesavailable to the user equipment. For example, the packet-switched domainprovides for data or voice services, whereas the circuit-switched domainprovides for voice or legacy messages.

The application server generates and transmits a query to a node of afirst domain. When a response from the node is negative (i.e., userequipment is not registered with the first domain), the applicationserver can either generate and transmit another query to a node of asecond domain or conclude that the user equipment is registered with thesecond domain. Generating and transmitting another query or concludingregistration to the second domain can increase latency or inhibit theavailability of certain services, thereby reducing the user or customerexperience. Generating and transmitting another query can also increasewasted signaling for the service provider.

What is needed is a telecommunications network having an improved domainrequest. What is further needed is a telecommunication network to moreefficiently request domain registration.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example network.

FIG. 2 illustrates a flowchart for an example process for requestingdomain registration.

FIG. 3 illustrates a user data request including a query hierarchy.

DETAILED DESCRIPTION

A system and method for determining registration of a UE to apacket-switching (PS) domain or a circuit-switching (CS) domain via asingle request is disclosed herein. A telecommunications networkincludes two domains: a packet-switched domain and a circuit-switcheddomain. A user equipment (UE) can be unregistered to either domain(i.e., the UE is powered off, detached from the telecommunicationsnetwork, or the like), registered to one domain, or registered to bothdomains. An application server, which is a component of thetelecommunications network, provides services to the UE. The applicationserver can determine the services available to the user equipment basedon the domain to which the UE is registered. For example, thepacket-switched domain provides for data or voice services, whereas thecircuit-switched domain provides for voice or legacy messages.

An application server (AS) generates a single request and queries a nodeto determine a domain with which the user equipment (UE) is registered(i.e., to determine which services are available to the UE) The nodebeing queried can respond that the UE is registered with or notregistered with the domain associated with the node.

The request includes a query hierarchy to query a node of a first domainand then, if the UE is not registered with the first domain, to query anode of a second domain. The request further prevents a conclusion thata negative response to a query inherently means that the UE is connectedto another domain. The request includes an attribute value pair (AVP) todetermine which domain to query first and which node of the first domainto query. The domains of the AVP are acquired from a list to permitmultiple domains to be queried with the single request. The AVP is acontainer of data that carries and includes information (e.g.,authentication, authorization, accounting, routing, security,capability, the like, and combinations or multiples thereof) betweennodes.

The system generates a request including a query hierarchy including anorder in which to query a first domain and a second domain. The requestalso includes an instruction to query a first node and, if a negativeresponse is received, to query a second node, such that the first andsecond nodes are associated with different domains. The system can thendetermine the domain to which a user equipment (UE) is registered basedon the response from the first node based on a first query, the secondnode based on a second query, or both. A notification can then begenerated which includes the domain with which the UE is registered.Services can then be executed or provided based on the domain to whichthe UE is registered.

By establishing the registered domain, the application server candetermine the services available to the user equipment. For example, thepacket-switched domain provides for data or voice services, whereas thecircuit-switched domain provides for voice or legacy messages.

FIG. 1 shows a system including a telecommunications network 100. Thetelecommunications network 100 includes an access network (e.g., GERAN;UTRAN; E-UTRAN; VoLTE; 5G NR; VoNR) 104 a-c which includes a networksite (e.g., BTS, NodeB, eNodeB, or gNB) 110 a-110 c. The access network104 a-c connects a user equipment (UE) 102 to a mobile communicationtechnology (e.g., 1G to 5G). The UE 102 can be connected to one or moreaccess networks 104 a-c simultaneously.

The UE 102 is any device used by an end-user for communication or datatransmission purposes, including, without limitation, a mobile phone, asmartphone, a tablet, a personal digital assistant, a laptop with mobileconnectivity, or the like.

When the access network 104 c is E-UTRAN, the network site 110 c is aneNodeB. The access network 104 c transmits data, including data packets,between the UE 102 and an external network 140, such as through a datacore 150. The network site 110 c controls the UE 102 within a given cellof the telecommunications network. For example, the network site 110 csends and receives radio transmission(s) to the UE 102 using analogueand digital signal processing functions of an access network airinterface. The network site 110 c also controls low-level operations ofthe UE 102 via signaling messages, such as handover commands.

The network site 110 c includes a UE communication module programmed tocommunicate with the UE 102 (i.e., transmit a signal or data). The UEcommunication module can be an interface, such as a UU or e-Uuinterface. The network site 110 c also includes a data corecommunication module programmed to communicate (i.e., transmit a signalor data) with the data core 150. The data core communication module canbe an interface, such as a S1, GTP, or NG interface.

The data core 150 is an IP-based core network infrastructure thatprovides packet data services, such as to support the convergence oflicensed and unlicensed radio technologies (e.g., an evolved packet core(EPC) or 5G Core). The data core 150 can be defined around variousparadigms, including mobility, policy management, and security. The fourelements of the data core include a home subscriber server (HSS) 114, amobility management entity (MME) 112, a serving gateway (SGW) 116, and apacket data network gateway (PGW) 118.

The MME 112 pages and authenticates the UE 102. The MME 112 can retainlocation information at the tracker level for each UE 102 and selectsthe appropriate gateway during the initial registration process. The MME112 can connect to the network site via a S1-MME interface and to theSGW 116 via a S11 interface.

The SGW 116 forwards and routes packets (e.g., data packets) to and fromthe network site and the PGW 118. The SGW 116 connects to the networksite via a S1-U and to the PGW 118 via a S5/S8 interface.

The PGW 118 provides connectivity between the UE 102 and the externalnetwork 140, including a public data network, an IP multimedia subsystem(IMS) core, the like, or combinations or multiples thereof. The PGW 118can be connected to the external network 140 via a SGi interface.

The HSS 114 of the data core 150, which is in communication with the MME112 via a S6 interface, is a database that contains user-relatedinformation and subscriber-related information. Though the HSS 114 isdiscussed as being a node of the data core 150, the HSS 114 can be anode of the external network 140 or a first HSS can be a node of thedata core 150 and a second HSS can be a node of the external network140.

The external network 140 can include an application server (AS) 142. TheAS 142 is a node that executes services (e.g., call forwarding) andfetches customer data (e.g., customer status, location information, orthe like). The AS 142 can communicate with the HSS 114 and the HLR 136via a Sh interface or MAP interface.

When the access network 104 a is GERAN, the network site 110 a is a basetransceiver station (BTS) which is controlled by a base stationcontroller (BSC) 106. The BTS includes equipment to transmit and receiveradio signals, antennas, and equipment to encrypt and decryptcommunications with the BSC 106. The BSC 106 can control multiple BTSs.The BSC 106 controls BTS handover, radio channel allocation, and UEmeasurements. The BTS and the BSC 106 are in communication via an Abisinterface.

The BSC 106 communicates with a mobile switching center/visitor locationregister (MSC/VLR) 132 of a circuit-switched (CS) domain 130 via an Ainterface. The MSC/VLR 132 routes voice calls, text messages (i.e.,short message service), and other services (e.g., conference calls, fax,CS data, or the like) and provides customer information when thecustomer is outside of the home network. The MSC/VLR 132 connects to anexternal network 140, such as a service switching point (SSP), via a CAPinterface. The SSP is a telephone exchange to perform call processing.The SSP applies an SS7 protocol to control or manage call setup, callhandling, and call termination with other SSPs.

The CS domain 130 also includes a home location register (HLR) 136. TheHLR 136 is a database including details of each customer authorized tothe CS domain 130. The MSC/VLR 132 communicates with the HLR 136 via aC, D, F, or H interface.

The CS domain 130 also includes a short message service center (SMSC)134, which is responsible for the delivery of the short message texts.The MSC/VLR 132 communicates with the SMSC 134 via an E interface.

The BSC 106 also communicates with a serving GPRS support node (SGSN)122 of a packet-switched (PS) domain 120 via a Gb interface. The SGSN122 handles PS data, including mobility management and customerauthentication. The SGSN 122 acts as the service access point for PSdomain 120 and handles protocol conversion for internet protocol withinthe PS domain 120. The SGSN 122 communicates with a gateway GPRS supportnode (GGSN) 124 via a Gn interface. The GGSN 124 provides connectivitybetween the UE 102 and the external network 140, such as an externaldata packet network, including a public data network, an IP multimediasubsystem (IMS) core, the like, or combinations or multiples thereof.The GGSN 124 can be connected to the external network 140 via a Giinterface.

The SGSN 122 of the PS domain 120 can communicate with the SMSC 134 ofthe CS domain 130 via a Gd interface, with the MSC/VLR 132 of the CSdomain 130 with a Gs interface, and with the HLR 136 of the CS domain130 via a Gr or Gf interface. The GGSN 124 of the PS domain 120 cancommunication with the HLR 136 of the CS domain 130 via a Gc interface.

When the access network 104 b is UTRAN, the network site 110 b is aNodeB which is controlled by the radio network controller (RNC) 108. TheNodeB includes equipment to transmit and receive radio signals,antennas, and equipment to encrypt and decrypt communications with theRNC 108. The RNC 108 can control multiple NodeBs. The RNC 108 controlsradio resource management, some mobility management functions, and dataencryption to and from the UE. The NodeB and the RNC 108 are incommunication via an IuB interface.

The RNC 108 communicates with the SGSN 122 of the PS domain via an IuPSinterface. The RNC 108 communicates with the MSC/VLR 132 of the CSdomain 130 via an IuCS interface. The RNC 108 communicates with the SGW116 of the data core 150 via a S12 interface.

FIG. 2 shows a flowchart for requesting domain registration. At 202, theapplication server generates a user data request (UDR) causes a query tobe transmitted to a node. The query, which includes a query hierarchy,can determine a domain with which the user equipment (UE) is registered(i.e., to determine which services are available to the UE). The queryhierarchy sets forth the order in which to query a node of a firstdomain for UE registration and then, if the UE is not registered withthe first domain, to query a node of a second domain for UEregistration. The application server queries the domains in a givenorder based on the query hierarchy listed in the AVP of the UDR.

FIG. 3 shows a user data request (UDR) 300. The UDR 300 includesattribute value pairs (AVPs) to structure a query hierarchy, therebysetting the order in which to query the domains and the order in whichto query the node or nodes of each respective domain. Each AVP includesan attribute 302 and a value 304. The value 304 is data or information.The attribute 302 is the field represented by the value 304. The UDR 300includes a domain attribute and a node attribute. The domain values caninclude “1” (for PS domain), “0” (for CS domain), or the values can beimported from a list of another attribute. The node values can include“1” (for SGSN), “0” (for MME), “0,1” or “1,0” (for both SGSN and MME inthe respective order) values, a “MSC/VLR” value, or the values can beimported from a list of another attribute.

The UDR 300 can include an AVP having a special attribute. The valuesassociated with the special attribute can be provided in a list. Thelist associated with the special attribute can be imported by one of theother attributes. This allows for multiple queries to be generated by asingle UDR rather than a single query based on a single request.

The UDR 300 can also include multiple AVPs with each AVP having aspecial attribute. Values of each of the special attributes can beprovided in a list. The lists associated with each of the specialattributes can be imported by the other attributes. This allows formultiples queries to be generated by a single UDR, rather than singlequery based on a single request.

For example, a UDR includes “requested domain,” “requested node,”special note 1,” and “special note 2” attributes. The “special note 1”includes a domain query hierarchy (i.e., order in which to querydomains). The “special note 2” includes a node query hierarchy (i.e.,order in which to query nodes of the respective domains). The “requesteddomain” imports the list associated with “special note 1” and the“requested node” imports the list associated with “special note 2.”

As another example, a UDR includes “requested domain,” “requested node,”special note 1,” and “special note 2” attributes. The “special note 1”includes a list to query the PS domain first and the CS domain second(e.g., “1,0”). The “special note 2” includes a list to query the MMEfirst and the SGSN second when querying the PS domain, then the MSC/VLRwhen querying the CS domain (e.g., “0,1,” MSC/VLR”). The “requesteddomain” imports the list associated with “special note 1” and the“requested node” imports the list associated with “special note 2.”Therefore, the UDR causes the MME to be queried first (PS domain), thenthe SGSN second (PS domain), and then the MSC/VLR third (CS domain).

Though two special notes are discussed, the domain and node hierarchiescan be provided in a single special note. Furthermore, though the listsare discussed as being imported by other attributes, the lists of oneattribute can be read or recalled by another attribute. Additionally, inone example, only the MSC/VLR node is queried for the CS domain, suchthat a value for the requested node associated with the CS domain is notrequired.

Returning to FIG. 2, at 204, the application server queries the node ofthe first domain based on the domain and node hierarchies. At 206, thenode of the first domain generates and transmits a response to theapplication server indicating whether or not the UE is registered to thefirst domain. In one example, multiples nodes of the first domain can bequeried, such as when a first node does not recognize UE registration.

At 208, when the UE is registered to the first domain, the nodegenerates a notification that the UE is registered with the first domain(i.e., “positive,” “UE is registered to first domain,” or the like).Since the UE is registered to the first domain, the second domain is notqueried. At 210, services available via the first domain can then beused or made available to the UE, such as via the application server.

At 212, when the UE is not registered to the first domain, the nodegenerates a notification that the UE is not registered with the firstdomain (i.e., “negative,” “UE is not registered to the first domain,” orthe like). The node retains the UDR until a positive response isreceived from a domain about UE registration. At 214, the node thenqueries the second domain based on the UDR. At 208, the node generatesand transmits a registration notification that the UE is registered withthe second domain. The node can be the HSS. At 210, services availablevia the second domain can then be used or made available to the UE, suchas via the application server.

For example, the application server generates a UDR including “requesteddomain,” “requested node,” special note 1,” and “special note 2”attributes. The “special note 1” includes a domain query hierarchy(i.e., order in which to query domains). The “special note 2” includes anode query hierarchy (i.e., order in which to query nodes of therespective domains). A first domain is a PS domain including a MME and aSGSN. A second domain is a CS domain including a MSC/VLR.

Embodiments of the invention can include a non-transitory computerreadable medium which can store instructions for performing theabove-described methods and any steps thereof, including anycombinations of the same. For example, the non-transitory computerreadable medium can store instructions for execution by one or moreprocessors or similar devices.

Further embodiments of the present invention can also include the one ormore user equipment(s), network sites, backend network, or servers whichread out and execute computer executable instructions, such as anon-transitory computer-readable medium, recorded or stored on a storagemedium (which may be the same as or different than the storage mediumfor storing images or files, as discussed above), to perform thefunctions of any embodiment. The user equipment or server may includeone or more of a central processing unit (CPU), micro processing unit(MPU), or other circuitry, such as a processor, and may include anetwork of separate user equipment or servers or separate computerprocessors. The computer executable instructions may be provided to theuser equipment, network node, or server, for example, from a network orthe storage medium.

Though certain elements, aspects, components or the like are describedin relation to one embodiment or example of a telecommunicationsnetwork, those elements, aspects, components or the like can beincluding with any other telecommunications network, such as when itdesirous or advantageous to do so.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the disclosure.However, it will be apparent to one skilled in the art that the specificdetails are not required in order to practice the systems and methodsdescribed herein. The foregoing descriptions of specific embodiments orexamples are presented by way of examples for purposes of illustrationand description. They are not intended to be exhaustive of or to limitthis disclosure to the precise forms described. Many modifications andvariations are possible in view of the above teachings. The embodimentsor examples are shown and described in order to best explain theprinciples of this disclosure and practical applications, to therebyenable others skilled in the art to best utilize this disclosure andvarious embodiments or examples with various modifications as are suitedto the particular use contemplated. It is intended that the scope ofthis disclosure be defined by the following claims and theirequivalents.

What is claimed is:
 1. An application server of a telecommunicationsnetwork, comprising: one or more processors; a memory storingcomputer-readable instructions that, when executed by the one or moreprocessors, cause the application server to: generate a request to afirst node and to determine a domain to which a UE is registered basedon the response from the first node, the request comprising: a queryhierarchy including an order in which to query a first domain and asecond domain, and an instruction to query the first node according tothe query hierarchy and, if a negative response is received, to query asecond node according to the query hierarchy, the first and second nodescoupled to the first and second domains, determine a domain of the firstand second domains to which the user equipment (UE) is registered basedon the response from the first node based on the instruction to querythe first node, the second node based on the instruction to query thesecond node, or both, the processor further configured to execute thecomputer-readable instructions to generate the request and to determinethe domain to which a UE is registered based on the response from thefirst node; and an output generating a notification including the domainwith which the UE is registered.
 2. The system of claim 1, wherein thequery hierarchy is based on an attribute value pair (AVP) including thefirst domain and the second domain.
 3. The system of claim 2, whereinthe AVP further comprises a domain list including the first and seconddomains.
 4. The system of claim 2, wherein the first domain is apacket-switched domain and the second domain is a circuit-switcheddomain.
 5. The system of claim 4, wherein the first node is a mobilitymanagement entity (MME) or a serving GPRS support node (SGSN).
 6. Thesystem of claim 1, further comprising a service node to execute networkservices based on the domain to which the UE is registered.
 7. Thesystem of claim 1, further comprising wherein the instruction is furtherconfigured to: query a third node, and if a negative response isreceived, to query the first node, the third and first nodes beingcoupled a similar domain.
 8. The system of claim 7, wherein the thirdnode is queried before the first node based on an AVP including thefirst and third nodes.
 9. The system of claim 7, wherein the first andthird nodes are associated with a packet-switched domain and the secondnode is associated with a circuit-switched domain.
 10. The system ofclaim 1, wherein the processor is further configured to receive theresponse from the first node based on the instruction to query the firstnode, the second node based on the instruction to query the second node,or both.
 11. A method for improving a user data request, comprising:generating, in response to an instruction received from a processor, arequest comprising: a query hierarchy including an order in which toquery a first domain and a second domain, and an instruction to query afirst node according to the query hierarchy and, if a negative responseis received, to query a second node according to the query hierarchy,the first and second nodes coupled to the first and second domains;determining a domain of the first and second domains to which a userequipment (UE) is registered based on a response from the first nodebased on the instruction to query the first node, the second node basedon the instruction to query the second node, or both; and generating anotification including the domain with which the UE is registered. 12.The method of claim 11, further comprising executing network servicesbased on the domain to which the UE is registered.
 13. The method ofclaim 12, further comprising a service node to execute network servicesbased on the domain to which the UE is registered.
 14. The method ofclaim 11, wherein the query hierarchy is based on an attribute valuepair (AVP) including the first domain and the second domain.
 15. Themethod of claim 14, wherein the AVP further comprises a domain listincluding the first and second domains.
 16. The method of claim 14,wherein the first domain is a packet-switched domain and the seconddomain is a circuit-switched domain.
 17. The method of claim 11, whereinthe instruction in the request includes an instruction to query a thirdnode according to the query hierarchy, and if a negative response isreceived, querying the first node, the third and first nodes beingassociated with the same domain.
 18. The method of claim 17, wherein thethird node is queried before the first node based on an AVP includingthe first and third nodes.
 19. The method of claim 17, wherein the firstand third nodes are associated with a packet-switched domain and thesecond node is associated with a circuit-switched domain.
 20. The methodof claim 11, further comprising receiving the response from the firstnode based on the instruction to query the first node, the second nodebased on the instruction to query the second node, or both.